Long Term Evolution Mobility Network Timer And Retry Management

ABSTRACT

Management of a network may be accomplished by adjusting timer settings and/or retry criteria. For example, communications and management from an end-to-end perspective of entities in a network may be conducted; timers and/or retry criteria may be adjusted dynamically based on network traffic load; timers and/or retry criteria may be adjusted dynamically based on overload conditions; feedback mechanisms may be implemented to allow downstream network elements to inform upstream network elements about the health status and/or load condition of the network; and/or differentiated timer and retry criteria/mechanisms may be implemented.

CROSS-REFERENCE TO RELATED APPLICATIONS

The instant application is a continuation of, and claims priority to,U.S. patent application Ser. No. 13/712,407, filed Dec. 12, 2012. U.S.patent application Ser. No. 13/712,407 is incorporated by referenceherein in its entirety.

TECHNICAL FIELD

The technical field generally relates to wireless communications andmore specifically relates to network timers and retry management in along term evolution (LTE) network.

BACKGROUND

When a problem arises with a communications device, such as a mobilephone or the like, attempting to connect and/or transmit to a network,the mobile phone may retry to connect and/or transmit. These retriedattempts could occur several times causing network congestions.

SUMMARY

Management of a long term evolution (LTE) mobility network may beaccomplished by adjusting timer settings and/or retrycriteria/mechanisms. For example, communications and management from anend-to-end perspective of entities in a network may be conducted. Timersand/or retry criteria/mechanisms may be adjusted dynamically based onnetwork traffic load. Timers and/or retry criteria/mechanisms may beadjusted dynamically based on overload conditions. Feedback mechanismsmay allow downstream network elements (e.g., home subscriber server,HSS) to communicate with upstream network elements (e.g., DiameterRouting Agent, DRA,) to inform upstream network elements about thehealth status and/or load condition of the network in order to allow theupstream network elements to adjust respective timers and retrymechanism accordingly. Differentiated timer and retrycriteria/mechanisms may be implemented when a single network elementcommunicates with multiple downstream network elements to allow forflexibility based on individual downstream network traffic and healthcondition.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference is made here to the accompanying drawings, which are notnecessarily drawn to scale.

FIG. 1 is a diagram of an example system and process for management oftimer settings and/or retry criteria/mechanisms.

FIG. 2 is another diagram of an example system and process formanagement timer settings and/or retry criteria/mechanisms.

FIG. 3 is another diagram of an example system and process formanagement of timer settings and/or retry criteria/mechanisms.

FIG. 4 is a block diagram of an example communications device that maybe utilized to manage timer settings and/or retry criteria/mechanisms.

FIG. 5 is a block diagram of an example network entity 90 that may beutilized to manage timer settings and/or retry criteria/mechanisms.

FIG. 6 is a diagram of an example communications system in whichmanagement of timer settings and/or retry criteria/mechanisms may beimplemented.

FIG. 7 is a system diagram of an example WTRU.

FIG. 8 is a system diagram of an example RAN and example core network.

FIG. 9 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network, withinwhich management of timer settings and/or retry criteria/mechanisms maybe implemented.

FIG. 10 illustrates an architecture of a typical GPRS network withinwhich management of timer settings and/or retry criteria/mechanisms maybe implemented.

FIG. 11 illustrates an example block diagram view of a GSM/GPRS/IPmultimedia network architecture within which management of timersettings and/or retry criteria/mechanisms may be implemented.

FIG. 12 illustrates a PLMN block diagram view of an example architecturein which management of timer settings and/or retry criteria/mechanismsmay be incorporated.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Aspects of the instant disclosure are described more fully herein withreference to the accompanying drawings, in which example embodiments areshown. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide anunderstanding of the various embodiments. However, the instantdisclosure may be embodied in many different forms and should not beconstrued as limited to the example embodiments set forth herein. Likenumbers refer to like elements throughout.

FIG. 1 is a diagram of an example system and process for management oftimer settings and/or retry criteria/mechanisms. As depicted in FIG. 1,a network may comprise multiple network entities as depicted by networkentity 12, network entity 14, network entity 16, and network entity 18.Each network entity may have a timer associated therewith. Each networkentity may have retry criteria associated therewith. In order to managethe network more efficiently and reduce the time to establishcommunications between network entities, various timer settingadjustments and/or retry criteria/mechanisms are described. It is to beunderstood that the network depicted in FIG. 1 is an example, and shouldnot be interpreted as limiting in structure, function, or the like.

In an example embodiment, end to end timer management of a network maybe implemented wherein a network entity in a network may a have greatertimeout value than its next lower level downstream network entity. Thismay reduce the time it takes to establish communications betweennetworks entities and manage the network more efficiently. When anetwork entity attempts to establish communication with another networkentity (depicted by steps 20, 22, 24), if the attempt fails, the networkentity may wait a period of time before retrying establishingcommunication with the other network entity. Thus, to avoid upstreamelements sending retransmissions while downstream elements are stillhandling the initial request, and to ensure timeout propagates fromdownstream to upstream, timer values may be decreased as the network istraversed downstream. For example network entity 12 may have a timervalue that is greater than the timer value for network entity 14.Network entity 14 may have a timer value that is greater than the timervalue for network entity 16. And network entity 16 may have a timervalue that is greater than the timer value for network entity 18. If anetwork entity existed (not depicted in FIG. 1) downstream of networkentity 18, network entity 18 may have a timer value that is greater thanthe timer value for that next downstream network entity 18.

In an example embodiment, end to end retry management of a network maybe implemented wherein a network entity in the network may have agreater maximum number of retries than the next lower level downstreamnetwork entity. This may reduce the time it takes to establishcommunications between networks entities and manage the network moreefficiently. When a network entity attempts to establish communication(depicted by steps 20, 22, 24) with a downstream network entity, if theattempt fails, the network entity may retry establishing communicationwith the downstream network. Accordingly, in an example embodiment, anupstream network entity may have a greater maximum number of retriesthan its next downstream network entity. For example network entity 12may have a maximum number of retries that is greater than the maximumnumber of retries for network entity 14. Network entity 14 may have amaximum number of retries that is greater than the maximum number ofretries for network entity 16. And network entity 16 may have a maximumnumber of retries that is greater than the maximum number of retries fornetwork entity 18.

In an example embodiment, end to end congestion feedback within anetwork may be implemented wherein a downstream network entity mayinform an upstream network entity about the health status and/or loadcondition of the network and/or the network entity. A downstream networkentity may feedback a congestion indicator, or the like, which mayinclude current status, historical information, future congestionlevels, etc., to upstream network entities. This may allow upstreamnetwork entities to adjust respective timers and retry mechanismaccordingly. For example, network entity 18 may determine, via anyappropriate process, mechanism, or the like, the amount of data traffic(data) it is processing, the amount of data it expects to process (e.g.,via a prediction mechanism, via scheduled events, etc.), whether theamount of data it is processing is over a threshold amount (e.g.,congestion), whether the amount of data it is processing is expected togo over a threshold amount (e.g., via prediction mechanism to determinepredicted congestion, via scheduled events to determine anticipatedcongestion, etc.), the amount of memory it is utilizing, the amount ofmemory it expects to utilize (e.g., via a prediction mechanism, viascheduled events, etc.), whether the amount of memory it is utilizing isover a threshold amount (e.g., congestion), whether the amount of memoryit is utilizing is expected to go over a threshold amount (e.g., viaprediction mechanism to determine predicted congestion, via scheduledevents to determine anticipated congestion, etc.), historicalinformation regarding processing, historical information regardingmemory, or any appropriate combination thereof. And the network entity18 may provide any or all of the aforementioned information to networkentity 16. Network entity 16 may provide the information received fromnetwork entity 18 to network entity 14. Network entity 16 may alsoprovide to network entity 14 any information that network entity 16determines about itself, such as, for example, information regardingprocessing and/or memory as describe above in this paragraph. Similarly,network 14 may provide to network entity 12, information received fromnetwork entity 16 (which may include information pertaining to networkentity 18, may include information pertaining to network entity 16, orany appropriate combination thereof). And network entity 14 may alsoprovide to network entity 12 any information that network entity 14determines about itself, such as, for example, information regardingprocessing and/or memory as describe above in this paragraph.

FIG. 2 is another diagram of an example system and process formanagement timer settings and/or retry criteria/mechanisms. In anexample embodiment, end to end differentiated timer and retrycriteria/mechanisms may be implemented wherein, when a single networkentity communicates with multiple downstream network entities, therespective timer value and/or retry criteria for each of the multipledownstream network entities may be based on a respective condition ofeach downstream network entity. For example, referring to FIG. 2,network entity 26 may determine the timer value and/or retry criteriafor each of network entity 28, network entity 30, and network entity 32.The determined timer values and/or retry criteria may be based on acondition of each of network entity 28, network entity 30, and networkentity 32. Thus, each of network entity 28, network entity 30, andnetwork entity 32 may have its own tailored timer value and/or retrycriteria. The condition may be based on processing and memory usage ofeach of network entity 28, network entity 30, and network entity 32. Forexample, network entity 28 may determine, via any appropriate process,mechanism, or the like, the amount of data traffic (data) it isprocessing, the amount of data it expects to process (e.g., via aprediction mechanism, via scheduled events, etc.), whether the amount ofdata it is processing is over a threshold amount (e.g., congestion),whether the amount of data it is processing is expected to go over athreshold amount (e.g., via prediction mechanism to determine predictedcongestion, via scheduled events to determine anticipated congestion,etc.), the amount of memory it is utilizing, the amount of memory itexpects to utilize (e.g., via a prediction mechanism, via scheduledevents, etc.), whether the amount of memory it is utilizing is over athreshold amount (e.g., congestion), whether the amount of memory it isutilizing is expected to go over a threshold amount (e.g., viaprediction mechanism to determine predicted congestion, via scheduledevents to determine anticipated congestion, etc.), historicalinformation regarding processing, historical information regardingmemory, or any appropriate combination thereof. This information may beprovided to network entity 26, and network entity 26 may determine atimer value and/or retry criteria (e.g., maximum number of retries)based on the information. Similarly, each of network entity 30 andnetwork entity 32 may determine respective processing and memory usageas described above, and provide this information to network entity 26.Network entity 26 may determine a timer value and/or retry criteria fornetwork entity 30 based on information received from network entity 30.And network entity 26 may determine a timer value and/or retry criteriafor network entity 32 based on information received from network entity32.

Network entities depicted in FIG. 2 may comprise any appropriate networkentity. For example, network entity 26 may comprise a DSR and each ofnetwork entity 28, network entity 30, and network entity 32 may comprisea HSS.

FIG. 3 is a diagram of an example system and process for management oftimer settings and/or retry criteria/mechanisms, wherein the networkentities comprise a mobile device (also referred to as user equipment orUE) 34, a mobility management entity (MME) 36, a Diameter signalingrouter (DSR) 38, and a home subscriber server (HSS) 40. As depicted inFIG. 1, a network may comprise multiple network entities as depicted bynetwork entity 12, network entity 14, network entity 16, and networkentity 18. Each network entity may have a timer associated therewith.Each network entity may have retry criteria associated therewith. Inorder to manage the network more efficiently and reduce the time toestablish communications between network entities, various timer settingadjustments and/or retry criteria/mechanisms are described. It is to beunderstood that the network depicted in FIG. 3 is an example, and shouldnot be interpreted as limiting in structure, function, or the like.

In an example embodiment, end to end timer management of a network maybe implemented wherein a network entity in a network may a have greatertimeout value than its next lower level downstream network entity. Thismay reduce the time it takes to establish communications betweennetworks entities and manage the network more efficiently. For example,the UE 34 may establish a timer (e.g., T3410 timeout) having a value of15 seconds, for a UE attach request. The MME may establish a timer(e.g., Diameter timeout) having a value of 10 seconds. The DSR mayestablish a timer (e.g., Diameter Routing Agent, DRA-DSR set up pendingtransaction timeout) having a value of 8 seconds. The HSS may establisha timer (e.g., Diameter session timer) having a value of 6 seconds. Andthe HSS may establish a timer of 3 seconds.

In an example embodiment, end to end retry management of a network maybe implemented wherein a network entity in the network may have agreater maximum number of retries than the next lower level downstreamnetwork entity. This may reduce the time it takes to establishcommunications between networks entities and manage the network moreefficiently. For example, the UE 34 may establish a timer (e.g., T3410retry) having a maximum number of retries of 12, for a UE attachrequest. The MME may establish a maximum number of retries (e.g., MMEDiameter retry) of 9. The DSR may establish a maximum number of retries(e.g., DRA-DSR pending transaction retry) of 6. The HSS may establish amaximum number of retries (e.g., Diameter session retry) of 4. And theHSS may establish a maximum number of retries of 2.

In an example embodiment, end to end congestion feedback within anetwork may be implemented wherein a downstream network entity mayinform an upstream network entity about the health status and/or loadcondition of the network and/or the network entity. A downstream networkentity may feedback a congestion indicator, or the like, which mayinclude current status, historical information, future congestionlevels, etc., to upstream network entities. This may allow upstreamnetwork entities to adjust respective timers and retry mechanismaccordingly. For example, HSS 40 may determine, via any appropriateprocess, mechanism, or the like, the amount of data traffic (data) it isprocessing, the amount of data it expects to process (e.g., via aprediction mechanism, via scheduled events, etc.), whether the amount ofdata it is processing is over a threshold amount (e.g., congestion),whether the amount of data it is processing is expected to go over athreshold amount (e.g., via prediction mechanism to determine predictedcongestion, via scheduled events to determine anticipated congestion,etc.), the amount of memory it is utilizing, the amount of memory itexpects to utilize (e.g., via a prediction mechanism, via scheduledevents, etc.), whether the amount of memory it is utilizing is over athreshold amount (e.g., congestion), whether the amount of memory it isutilizing is expected to go over a threshold amount (e.g., viaprediction mechanism to determine predicted congestion, via scheduledevents to determine anticipated congestion, etc.), historicalinformation regarding processing, historical information regardingmemory, or any appropriate combination thereof. And HSS 40 may provideany or all of the aforementioned information to DSR 38. DSR 38 mayprovide the information received from HSS 40 to MME 36. DSR 38 may alsoprovide to MME 36 any information that DSR 38 determines about itself,such as, for example, information regarding processing and/or memory asdescribe above in this paragraph. Similarly, MME 36 may provide to UE34, information received from DSR 38 (which may include informationpertaining to HSS 40, may include information pertaining to DSR 38, orany appropriate combination thereof). And MME 36 may also provide to UE34 any information that MME 36 determines about itself, such as, forexample, information regarding processing and/or memory as describeabove in this paragraph.

FIG. 4 is a block diagram of an example communications device 80 thatmay be utilized to manage timer settings and/or retrycriteria/mechanisms. In an example embodiment, the communications device80 may comprise the mobile device (UE) 12, 26. In an exampleconfiguration, communications device 80 comprises a mobile wirelessdevice. The communications device 80, however, may comprise anyappropriate device, examples of which include a portable computingdevice, such as a laptop, a personal digital assistant (“PDA”), aportable phone (e.g., a cell phone or the like, a smart phone, a videophone), a portable email device, a portable gaming device, a TV, a DVDplayer, portable media player, (e.g., a portable music player, such asan MP3 player, a Walkman, etc.), a portable navigation device (e.g., GPScompatible device, A-GPS compatible device, etc.), or a combinationthereof. The communications device 80 can include devices that are nottypically thought of as portable, such as, for example, a publiccomputing device, a navigation device installed in-vehicle, a set topbox, or the like. The mobile communications device 80 can includenon-conventional computing devices, such as, for example, a kitchenappliance, a motor vehicle control (e.g., steering wheel), etc., or thelike. As evident from the herein description a communications device, amobile device, or any portion thereof is not to be construed as softwareper se.

The communications device 80 may include any appropriate device,mechanism, software, and/or hardware for facilitating management oftimer settings and/or retry criteria/mechanisms as described herein. Inan example embodiment, the ability to facilitate management of timersettings and/or retry criteria/mechanisms is a feature of thecommunications device 80 that can be turned on and off Thus, in anexample embodiment, an owner of the communications device 80 may opt-inor opt-out of this capability.

In an example embodiment, the communications device 80 comprises aprocessor and memory coupled to the processor. The memory may compriseexecutable instructions that when executed by the processor cause theprocessor to effectuate operations associated with managing timersettings and/or retry criteria/mechanisms.

In an example configuration, the communications device 80 comprises aprocessing portion 82, a memory portion 84, an input/output portion 86,and a user interface (UI) portion 88. Each portion of the communicationsdevice 80 comprises circuitry for performing functions associated witheach respective portion. Thus, each portion can comprise hardware, or acombination of hardware and software. Accordingly, each portion of thecommunications device 80 is not to be construed as software per se. Itis emphasized that the block diagram depiction of communications device80 is exemplary and not intended to imply a specific implementationand/or configuration. For example, in an example configuration, thecommunications device 80 may comprise a cellular phone and theprocessing portion 82 and/or the memory portion 84 may be implemented,in part or in total, on a subscriber identity module (SIM) of the mobilecommunications device 80. In another example configuration, thecommunications device 80 may comprise a laptop computer. The laptopcomputer can include a SIM, and various portions of the processingportion 82 and/or the memory portion 84 can be implemented on the SIM,on the laptop other than the SIM, or any combination thereof.

The processing portion 82, memory portion 84, and input/output portion86 are coupled together to allow communications therebetween. In variousembodiments, the input/output portion 86 comprises a receiver of thecommunications device 80, a transmitter of the communications device 80,or a combination thereof. The input/output portion 86 is capable ofreceiving and/or providing information pertaining to management of timersettings and/or retry criteria/mechanisms as described herein. Invarious configurations, the input/output portion 86 may receive and/orprovide information via any appropriate means, such as, for example,optical means (e.g., infrared), electromagnetic means (e.g., RF, WI-FI,BLUETOOTH, ZIGBEE, etc.), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.

The processing portion 82 may be capable of performing functionspertaining to management of timer settings and/or retrycriteria/mechanisms as described herein. In a basic configuration, thecommunications device 80 may include at least one memory portion 84. Thememory portion 84 may comprise a storage medium having a tangiblephysical structure. Thus, the memory portion 84, as well as anycomputer-readable storage medium described herein, is not to beconstrued as a transient signal per se. Further, the memory portion 84,as well as any computer-readable storage medium described herein, is notto be construed as a propagating signal per se. The memory portion 84may store any information utilized in conjunction with management oftimer settings and/or retry criteria/mechanisms as described herein.Depending upon the exact configuration and type of processor, the memoryportion 84 may be volatile (such as some types of RAM), non-volatile(such as ROM, flash memory, etc.), or a combination thereof. The mobilecommunications device 80 may include additional storage (e.g., removablestorage and/or non-removable storage) including, but not limited to,tape, flash memory, smart cards, CD-ROM, digital versatile disks (DVD)or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, universal serial bus(USB) compatible memory, or any other medium which can be used to storeinformation and which can be accessed by the mobile communicationsdevice 80.

The communications device 80 also may contain a user interface (UI)portion 88 allowing a user to communicate with the communications device80. The UI portion 88 may be capable of rendering any informationutilized in conjunction with management of timer settings and/or retrycriteria/mechanisms as described herein. The UI portion 88 may providethe ability to control the communications device 80, via, for example,buttons, soft keys, voice actuated controls, a touch screen, movement ofthe mobile communications device 80, visual cues (e.g., moving a hand infront of a camera on the mobile communications device 80), or the like.The UI portion 88 may provide visual information (e.g., via a display),audio information (e.g., via speaker), mechanically (e.g., via avibrating mechanism), or a combination thereof. In variousconfigurations, the UI portion 88 may comprise a display, a touchscreen, a keyboard, an accelerometer, a motion detector, a speaker, amicrophone, a camera, a tilt sensor, or any combination thereof. The UIportion 88 may comprise means for inputting biometric information, suchas, for example, fingerprint information, retinal information, voiceinformation, and/or facial characteristic information.

The UI portion 88 may include a display for displaying multimedia suchas, for example, application graphical user interfaces (GUIs), text,images, video, telephony functions such as Caller ID data, setupfunctions, menus, music, metadata, messages, wallpaper, graphics,Internet content, device status, preferences settings, map and locationdata, routes and other directions, points of interest (POI), and thelike.

In some embodiments, the UI portion may comprise a user interface (UI)application. The UI application may interface with a client or operatingsystem (OS) to, for example, facilitate user interaction with devicefunctionality and data. The UI application may aid a user in enteringmessage content, viewing received messages, answering/initiating calls,entering/deleting data, entering and setting user IDs and passwords,configuring settings, manipulating content and/or settings, interactingwith other applications, or the like, and may aid the user in inputtingselections associated with management of timer settings and/or retrycriteria/mechanisms as described herein.

FIG. 5 is a block diagram of an example network entity 90 that may beutilized to manage timer settings and/or retry criteria/mechanisms. Thenetwork entity 90 may comprise hardware or a combination of hardware andsoftware. When used in conjunction with a network, the functionalityneeded to facilitate management of timer settings and/or retrycriteria/mechanisms can reside in any one or combination of networkentities. The network entity 90 depicted in FIG. 5 represents anyappropriate network entity, or combination of network entities, such as,for example, a processor, a server, a gateway, a node, any appropriateentity depicted in FIG. 1, any appropriate entity depicted in FIG. 2,any appropriate entity depicted in FIG. 3, any appropriate entitydepicted in FIG. 6 through FIG. 12, or any appropriate combinationthereof. In an example configuration, the network entity 90 may comprisea component or various components of a cellular broadcast systemwireless network. It is emphasized that the block diagram depicted inFIG. 5 is exemplary and not intended to imply a specific implementationor configuration. Thus, the network entity 90 may be implemented in asingle processor or multiple processors (e.g., single server or multipleservers, single gateway or multiple gateways, etc.). Multiple networkentities can be distributed or centrally located. Multiple networkentities can communicate wirelessly, via hard wire, or a combinationthereof.

In an example embodiment, the network entity 90 may comprise a processorand memory coupled to the processor. The memory may comprise executableinstructions that when executed by the processor cause the processor toeffectuate operations associated with management of timer settingsand/or retry criteria/mechanisms. As evident from the herein descriptiona network entity or any portion thereof is not to be construed assoftware per se.

In an example configuration, the network entity 90 may comprise aprocessing portion 92, a memory portion 94, and an input/output portion96. The processing portion 92, memory portion 94, and input/outputportion 96 may be coupled together (coupling not shown in FIG. 5) toallow communications therebetween. The input/output portion 96 may becapable of receiving and/or providing information from/to acommunications device and/or other network entities configured to beutilized with management of timer settings and/or retrycriteria/mechanisms. For example, the input/output portion 96 mayinclude a wireless communications (e.g., 2.5G/3G/4G/GPS) card. Theinput/output portion 96 may be capable of receiving and/or sending videoinformation, audio information, control information, image information,data, or any combination thereof. In an example embodiment, theinput/output portion 36 may be capable of receiving and/or sendinginformation to determine a location of the network entity 90 and/or thecommunications device 30. In an example configuration, the input\outputportion 96 may comprise a GPS receiver. In an example configuration, thenetwork entity 90 may determine its own geographical location and/or thegeographical location of a communications device through any type oflocation determination system including, for example, the GlobalPositioning System (GPS), assisted GPS (A-GPS), time difference ofarrival calculations, configured constant location (in the case ofnon-moving devices), any combination thereof, or any other appropriatemeans. In various configurations, the input/output portion 96 mayreceive and/or provide information via any appropriate means, such as,for example, optical means (e.g., infrared), electromagnetic means(e.g., RF, WI-FI, BLUETOOTH, ZIGBEE, etc.), acoustic means (e.g.,speaker, microphone, ultrasonic receiver, ultrasonic transmitter), or acombination thereof. In an example configuration, the input/outputportion may comprise a WIFI finder, a two way GPS chipset or equivalent,or the like, or a combination thereof.

The processing portion 92 may be capable of performing functionsassociated with management of timer settings and/or retrycriteria/mechanisms as described herein. That is, a communicationsdevice can perform functions internally (by the device) and/or utilizethe network entity 90 to perform functions. For example, the processingportion 92 may be capable of, in conjunction with any other portion ofthe network entity 90, installing an application for management of timersettings and/or retry criteria/mechanisms management of timer settingsand/or retry criteria/mechanisms. The processing portion 92, inconjunction with any other portion of the network entity 90, enables thenetwork entity 90 to covert speech to text when it is configured to alsosend text messages while utilizing the event based service.

In a basic configuration, the network entity 90 may include at least onememory portion 94. The memory portion 94 may comprise a storage mediumhaving a tangible physical structure. Thus, the memory portion 94, aswell as any computer-readable storage medium described herein, is not tobe construed as a transient signal per se. The memory portion 94, aswell as any computer-readable storage medium described herein, is not tobe construed as a propagating signal per se. The memory portion 94 maystore any information utilized in conjunction with management of timersettings and/or retry criteria/mechanisms as described herein. Dependingupon the exact configuration and type of processor, the memory portion94 may be volatile 98 (such as some types of RAM), non-volatile 100(such as ROM, flash memory, etc.), or a combination thereof. The networkentity 90 may include additional storage (e.g., removable storage 102and/or non-removable storage 104) including, but not limited to, tape,flash memory, smart cards, CD-ROM, digital versatile disks (DVD) orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, universal serial bus (USB)compatible memory, or any other medium which can be used to storeinformation and which can be accessed by the network entity 90.

The network entity 90 also may contain communications connection(s) 110that allow the network entity 90 to communicate with other devices,network entities, or the like. A communications connection(s) cancomprise communication media. Communication media typically embodycomputer readable instructions, data structures, program modules orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any information delivery media. By wayof example, and not limitation, communication media include wired mediasuch as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared, and other wireless media. The termcomputer readable media as used herein includes both storage media andcommunication media. The network entity 90 also can include inputdevice(s) 106 such as keyboard, mouse, pen, voice input device, touchinput device, etc. Output device(s) 108 such as a display, speakers,printer, etc. also can be included.

A communications device and/or network entity may be part of and/or incommunications with various wireless communications networks. Some ofwhich are described below.

FIG. 6 is a diagram of an example communications system in whichmanagement of timer settings and/or retry criteria/mechanisms may beimplemented. The communications system 100 may be a multiple accesssystem that provides content, such as voice, data, video, messaging,broadcast, etc., to multiple wireless users. The communications system100 may enable multiple wireless users to access such content throughthe sharing of system resources, including wireless bandwidth. Forexample, the communications systems 100 may employ one or more channelaccess methods, such as code division multiple access (CDMA), timedivision multiple access (TDMA), frequency division multiple access(FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and thelike. A communications system such as that shown in FIG. 6 may also bereferred to herein as a network.

As shown in FIG. 6, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a radioaccess network (RAN) 104, a core network 106, a public switchedtelephone network (PSTN) 108, the Internet 110, and other networks 112,though it will be appreciated that the disclosed embodiments contemplateany number of WTRUs, base stations, networks, and/or network elements.Each of the WTRUs 102 a, 102 b, 102 c, 102 d may be any type of deviceconfigured to operate and/or communicate in a wireless environment. Forexample, a WTRU may comprise network entity 12, network entity 26, a UE,or the like, or any combination thereof. By way of example, the WTRUs102 a, 102 b, 102 c, 102 d may be configured to transmit and/or receivewireless signals and may include user equipment (UE), a mobile station,a mobile device, a fixed or mobile subscriber unit, a pager, a cellulartelephone, a personal digital assistant (PDA), a smartphone, a laptop, anetbook, a personal computer, a wireless sensor, consumer electronics,and the like.

The communications systems 100 may also include a base station 114 a anda base station 114 b. Each of the base stations 114 a, 114 b may be anytype of device configured to wirelessly interface with at least one ofthe WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to one or morecommunication networks, such as the core network 106, the Internet 110,and/or the networks 112. By way of example, the base stations 114 a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a HomeNode B, a Home eNode B, a site controller, an access point (AP), awireless router, and the like. While the base stations 114 a, 114 b areeach depicted as a single element, it will be appreciated that the basestations 114 a, 114 b may include any number of interconnected basestations and/or network elements.

The base station 114 a may be part of the RAN 104, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, etc. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals within aparticular geographic region, which may be referred to as a cell (notshown). The cell may further be divided into cell sectors. For example,the cell associated with the base station 114 a may be divided intothree sectors. Thus, in an embodiment, the base station 114 a mayinclude three transceivers, i.e., one for each sector of the cell. Inanother embodiment, the base station 114 a may employ multiple-inputmultiple output (MIMO) technology and, therefore, may utilize multipletransceivers for each sector of the cell.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, infrared (IR), ultraviolet (UV), visible light, etc.). Theair interface 116 may be established using any suitable radio accesstechnology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104 and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish the air interface 116 using wideband CDMA (WCDMA). WCDMAmay include communication protocols such as High-Speed Packet Access(HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed DownlinkPacket Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

In another embodiment, the base station 114 a and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish the air interface116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.16 (i.e.,Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000,CDMA2000 1x, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), InterimStandard 95 (IS-95), Interim Standard 856 (IS-856), Global System forMobile communications (GSM), Enhanced Data rates for GSM Evolution(EDGE), GSM EDGE (GERAN), and the like.

The base station 114 b in FIG. 6 may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, and the like. In oneembodiment, the base station 114 b and the WTRUs 102 c, 102 d mayimplement a radio technology such as IEEE 802.11 to establish a wirelesslocal area network (WLAN). In another embodiment, the base station 114 band the WTRUs 102 c, 102 d may implement a radio technology such as IEEE802.15 to establish a wireless personal area network (WPAN). In yetanother embodiment, the base station 114 b and the WTRUs 102 c, 102 dmay utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE,LTE-A, etc.) to establish a picocell or femtocell. As shown in FIG. 6,the base station 114 b may have a direct connection to the Internet 110.Thus, the base station 114 b may not be required to access the Internet110 via the core network 106.

The RAN 104 may be in communication with the core network 106, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. For example, the core network 106may provide call control, billing services, mobile location-basedservices, pre-paid calling, Internet connectivity, video distribution,etc., and/or perform high-level security functions, such as userauthentication. Although not shown in FIG. 6, it will be appreciatedthat the RAN 104 and/or the core network 106 may be in direct orindirect communication with other RANs that employ the same RAT as theRAN 104 or a different RAT. For example, in addition to being connectedto the RAN 104, which may be utilizing an E-UTRA radio technology, thecore network 106 may also be in communication with another RAN (notshown) employing a GSM radio technology.

The core network 106 may also serve as a gateway for the WTRUs 102 a,102 b, 102 c, 102 d to access the PSTN 108, the Internet 110, and/orother networks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) andthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired or wireless communications networks ownedand/or operated by other service providers. For example, the networks112 may include another core network connected to one or more RANs,which may employ the same RAT as the RAN 104 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities, i.e., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks. For example, the WTRU 102 c shown in FIG. 6 may be configured tocommunicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 7 is a system diagram of an example WTRU 102. As shown in FIG. 7,the WTRU 102 may include a processor 118, a transceiver 120, atransmit/receive element 122, a speaker/microphone 124, a keypad 126, adisplay/touchpad 128, non-removable memory 130, removable memory 132, apower source 134, a global positioning system (GPS) chipset 136, andother peripherals 138. It will be appreciated that the WTRU 102 mayinclude any sub-combination of the foregoing elements while remainingconsistent with an embodiment.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Array (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 7depicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In another embodiment, the transmit/receiveelement 122 may be an emitter/detector configured to transmit and/orreceive IR, UV, or visible light signals, for example. In yet anotherembodiment, the transmit/receive element 122 may be configured totransmit and receive both RF and light signals. It will be appreciatedthat the transmit/receive element 122 may be configured to transmitand/or receive any combination of wireless signals.

In addition, although the transmit/receive element 122 is depicted inFIG. 7 as a single element, the WTRU 102 may include any number oftransmit/receive elements 122. More specifically, the WTRU 102 mayemploy MIMO technology. Thus, in one embodiment, the WTRU 102 mayinclude two or more transmit/receive elements 122 (e.g., multipleantennas) for transmitting and receiving wireless signals over the airinterface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 130 and/or the removable memory 132.The non-removable memory 130 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In other embodiments, the processor 118 may accessinformation from, and store data in, memory that is not physicallylocated on the WTRU 102, such as on a server or a home computer (notshown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, and the like.

FIG. 8 is an example system diagram of RAN 104 and core network 106. Asnoted above, the RAN 104 may employ an E-UTRA radio technology tocommunicate with the WTRUs 102 a, 102 b, and 102 c over the airinterface 116. The RAN 104 may also be in communication with the corenetwork 106.

The RAN 104 may include eNode-Bs 140 a, 140 b, 140 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an embodiment. The eNode-Bs 140 a, 140 b, 140c may each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the eNode-Bs 140 a, 140 b, 140 c may implement MIMO technology. Thus,the eNode-B 140 a, for example, may use multiple antennas to transmitwireless signals to, and receive wireless signals from, the WTRU 102 a.

Each of the eNode-Bs 140 a, 140 b, and 140 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the uplink and/or downlink, and the like. As shown in FIG. 8, theeNode-Bs 140 a, 140 b, 140 c may communicate with one another over an X2interface.

The core network 106 shown in FIG. 8 may include a mobility managementgateway or entity (MME) 142, a serving gateway 144, and a packet datanetwork (PDN) gateway 146. While each of the foregoing elements aredepicted as part of the core network 106, it will be appreciated thatany one of these elements may be owned and/or operated by an entityother than the core network operator.

The MME 142 may be connected to each of the eNode-Bs 140 a, 140 b, 140 cin the RAN 104 via an S1 interface and may serve as a control node. Forexample, the MME 142 may be responsible for authenticating users of theWTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting aparticular serving gateway during an initial attach of the WTRUs 102 a,102 b, 102 c, and the like. The MME 142 may also provide a control planefunction for switching between the RAN 104 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

The serving gateway 144 may be connected to each of the eNode-Bs 140 a,140 b, and 140 c in the RAN 104 via the S1 interface. The servinggateway 144 may generally route and forward user data packets to/fromthe WTRUs 102 a, 102 b, 102 c. The serving gateway 144 may also performother functions, such as anchoring user planes during inter-eNode Bhandovers, triggering paging when downlink data is available for theWTRUs 102 a, 102 b, 102 c, managing and storing contexts of the WTRUs102 a, 102 b, 102 c, and the like.

The serving gateway 144 may also be connected to the PDN gateway 146,which may provide the WTRUs 102 a, 102 b, 102 c with access topacket-switched networks, such as the Internet 110, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and IP-enableddevices.

The core network 106 may facilitate communications with other networks.For example, the core network 106 may provide the WTRUs 102 a, 102 b,102 c with access to circuit-switched networks, such as the PSTN 108, tofacilitate communications between the WTRUs 102 a, 102 b, 102 c andtraditional land-line communications devices. For example, the corenetwork 106 may include, or may communicate with, an IP gateway (e.g.,an IP multimedia subsystem (IMS) server) that serves as an interfacebetween the core network 106 and the PSTN 108. In addition, the corenetwork 106 may provide the WTRUs 102 a, 102 b, 102 c with access to thenetworks 112, which may include other wired or wireless networks thatare owned and/or operated by other service providers.

FIG. 9 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network, withinwhich management of timer settings and/or retry criteria/mechanisms maybe implemented. In the example packet-based mobile cellular networkenvironment shown in FIG. 9, there are a plurality of Base StationSubsystems (“BSS”) 800 (only one is shown), each of which comprises aBase Station Controller (“BSC”) 802 serving a plurality of BaseTransceiver Stations (“BTS”) such as BTSs 804, 806, and 808. BTSs 804,806, 808, etc. are the access points where users of packet-based mobiledevices become connected to the wireless network. In example fashion,the packet traffic originating from user devices is transported via anover-the-air interface to a BTS 808, and from the BTS 808 to the BSC802. Base station subsystems, such as BSS 800, are a part of internalframe relay network 810 that can include Service GPRS Support Nodes(“SGSN”) such as SGSN 812 and 814. Each SGSN is connected to an internalpacket network 820 through which a SGSN 812, 814, etc. can route datapackets to and from a plurality of gateway GPRS support nodes (GGSN)822, 824, 826, etc. As illustrated, SGSN 814 and GGSNs 822, 824, and 826are part of internal packet network 820. Gateway GPRS serving nodes 822,824 and 826 mainly provide an interface to external Internet Protocol(“IP”) networks such as Public Land Mobile Network (“PLMN”) 850,corporate intranets 840, or Fixed-End System (“FES”) or the publicInternet 830. As illustrated, subscriber corporate network 840 may beconnected to GGSN 824 via firewall 832; and PLMN 850 is connected toGGSN 824 via boarder gateway router 834. The Remote AuthenticationDial-In User Service (“RADIUS”) server 842 may be used for callerauthentication when a user of a mobile cellular device calls corporatenetwork 840.

Generally, there can be a several cell sizes in a GSM network, referredto as macro, micro, pico, femto and umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential, or smallbusiness environments. On the other hand, umbrella cells are used tocover shadowed regions of smaller cells and fill in gaps in coveragebetween those cells.

FIG. 10 illustrates an architecture of a typical GPRS network withinwhich management of timer settings and/or retry criteria/mechanisms maybe implemented. The architecture depicted in FIG. 10 is segmented intofour groups: users 950, radio access network 960, core network 970, andinterconnect network 980. Users 950 comprise a plurality of end users.Note, device 912 is referred to as a mobile subscriber in thedescription of network shown in FIG. 10. In an example embodiment, thedevice depicted as mobile subscriber 912 comprises a communicationsdevice (e.g., communications device 160). Radio access network 960comprises a plurality of base station subsystems such as BSSs 962, whichinclude BTSs 964 and BSCs 966. Core network 970 comprises a host ofvarious network elements. As illustrated in FIG. 10, core network 970may comprise Mobile Switching Center (“MSC”) 971, Service Control Point(“SCP”) 972, gateway MSC 973, SGSN 976, Home Location Register (“HLR”)974, Authentication Center (“AuC”) 975, Domain Name Server (“DNS”) 977,and GGSN 978. Interconnect network 980 also comprises a host of variousnetworks and other network elements. As illustrated in FIG. 10,interconnect network 980 comprises Public Switched Telephone Network(“PSTN”) 982, Fixed-End System (“FES”) or Internet 984, firewall 988,and Corporate Network 989.

A mobile switching center can be connected to a large number of basestation controllers. At MSC 971, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (“PSTN”) 982 through Gateway MSC(“GMSC”) 973, and/or data may be sent to SGSN 976, which then sends thedata traffic to GGSN 978 for further forwarding.

When MSC 971 receives call traffic, for example, from BSC 966, it sendsa query to a database hosted by SCP 972. The SCP 972 processes therequest and issues a response to MSC 971 so that it may continue callprocessing as appropriate.

The HLR 974 is a centralized database for users to register to the GPRSnetwork. HLR 974 stores static information about the subscribers such asthe International Mobile Subscriber Identity (“IMSI”), subscribedservices, and a key for authenticating the subscriber. HLR 974 alsostores dynamic subscriber information such as the current location ofthe mobile subscriber. Associated with HLR 974 is AuC 975. AuC 975 is adatabase that contains the algorithms for authenticating subscribers andincludes the associated keys for encryption to safeguard the user inputfor authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 10, whenmobile subscriber 912 initiates the attach process by turning on thenetwork capabilities of the mobile device, an attach request is sent bymobile subscriber 912 to SGSN 976. The SGSN 976 queries another SGSN, towhich mobile subscriber 912 was attached before, for the identity ofmobile subscriber 912. Upon receiving the identity of mobile subscriber912 from the other SGSN, SGSN 976 requests more information from mobilesubscriber 912. This information is used to authenticate mobilesubscriber 912 to SGSN 976 by HLR 974. Once verified, SGSN 976 sends alocation update to HLR 974 indicating the change of location to a newSGSN, in this case SGSN 976. HLR 974 notifies the old SGSN, to whichmobile subscriber 912 was attached before, to cancel the locationprocess for mobile subscriber 912. HLR 974 then notifies SGSN 976 thatthe location update has been performed. At this time, SGSN 976 sends anAttach Accept message to mobile subscriber 912, which in turn sends anAttach Complete message to SGSN 976.

After attaching itself with the network, mobile subscriber 912 then goesthrough the authentication process. In the authentication process, SGSN976 sends the authentication information to HLR 974, which sendsinformation back to SGSN 976 based on the user profile that was part ofthe user's initial setup. The SGSN 976 then sends a request forauthentication and ciphering to mobile subscriber 912. The mobilesubscriber 912 uses an algorithm to send the user identification (ID)and password to SGSN 976. The SGSN 976 uses the same algorithm andcompares the result. If a match occurs, SGSN 976 authenticates mobilesubscriber 912.

Next, the mobile subscriber 912 establishes a user session with thedestination network, corporate network 989, by going through a PacketData Protocol (“PDP”) activation process. Briefly, in the process,mobile subscriber 912 requests access to the Access Point Name (“APN”),for example, UPS.com, and SGSN 976 receives the activation request frommobile subscriber 912. SGSN 976 then initiates a Domain Name Service(“DNS”) query to learn which GGSN node has access to the UPS.com APN.The DNS query is sent to the DNS server within the core network 970,such as DNS 977, which is provisioned to map to one or more GGSN nodesin the core network 970. Based on the APN, the mapped GGSN 978 canaccess the requested corporate network 989. The SGSN 976 then sends toGGSN 978 a Create Packet Data Protocol (“PDP”) Context Request messagethat contains necessary information. The GGSN 978 sends a Create PDPContext Response message to SGSN 976, which then sends an Activate PDPContext Accept message to mobile subscriber 912.

Once activated, data packets of the call made by mobile subscriber 912can then go through radio access network 960, core network 970, andinterconnect network 980, in a particular fixed-end system or Internet984 and firewall 988, to reach corporate network 989.

FIG. 11 illustrates an example block diagram view of a GSM/GPRS/IPmultimedia network architecture within which management of timersettings and/or retry criteria/mechanisms may be implemented. Asillustrated, the architecture of FIG. 11 includes a GSM core network1001, a GPRS network 1030 and an IP multimedia network 1038. The GSMcore network 1001 includes a Mobile Station (MS) 1002, at least one BaseTransceiver Station (BTS) 1004 and a Base Station Controller (BSC) 1006.The MS 1002 is physical equipment or Mobile Equipment (ME), such as amobile phone or a laptop computer that is used by mobile subscribers,with a Subscriber identity Module (SIM) or a Universal IntegratedCircuit Card (UICC). The SIM or UICC includes an International MobileSubscriber Identity (IMSI), which is a unique identifier of asubscriber. The BTS 1004 is physical equipment, such as a radio tower,that enables a radio interface to communicate with the MS. Each BTS mayserve more than one MS. The BSC 1006 manages radio resources, includingthe BTS. The BSC may be connected to several BTSs. The BSC and BTScomponents, in combination, are generally referred to as a base station(BSS) or radio access network (RAN) 1003.

The GSM core network 1001 also includes a Mobile Switching Center (MSC)1008, a Gateway Mobile Switching Center (GMSC) 1010, a Home LocationRegister (HLR) 1012, Visitor Location Register (VLR) 1014, anAuthentication Center (AuC) 1018, and an Equipment Identity Register(EIR) 1016. The MSC 1008 performs a switching function for the network.The MSC also performs other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1010 provides a gateway between the GSM network and other networks, suchas an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1020. Thus, the GMSC 1010 providesinterworking functionality with external networks.

The HLR 1012 is a database that contains administrative informationregarding each subscriber registered in a corresponding GSM network. TheHLR 1012 also contains the current location of each MS. The VLR 1014 isa database that contains selected administrative information from theHLR 1012. The VLR contains information necessary for call control andprovision of subscribed services for each MS currently located in ageographical area controlled by the VLR. The HLR 1012 and the VLR 1014,together with the MSC 1008, provide the call routing and roamingcapabilities of GSM. The AuC 1016 provides the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. The EIR 1018 storessecurity-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 1009 allows one-to-one ShortMessage Service (SMS) messages to be sent to/from the MS 1002. A PushProxy Gateway (PPG) 1011 is used to “push” (i.e., send without asynchronous request) content to the MS 1002. The PPG 1011 acts as aproxy between wired and wireless networks to facilitate pushing of datato the MS 1002. A Short Message Peer to Peer (SMPP) protocol router 1013is provided to convert SMS-based SMPP messages to cell broadcastmessages. SMPP is a protocol for exchanging SMS messages between SMSpeer entities such as short message service centers. The SMPP protocolis often used to allow third parties, e.g., content suppliers such asnews organizations, to submit bulk messages.

To gain access to GSM services, such as speech, data, and short messageservice (SMS), the MS first registers with the network to indicate itscurrent location by performing a location update and IMSI attachprocedure. The MS 1002 sends a location update including its currentlocation information to the MSCNLR, via the BTS 1004 and the BSC 1006.The location information is then sent to the MS's HLR. The HLR isupdated with the location information received from the MSCNLR. Thelocation update also is performed when the MS moves to a new locationarea. Typically, the location update is periodically performed to updatethe database as location updating events occur.

The GPRS network 1030 is logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1032, a cell broadcast and a GatewayGPRS support node (GGSN) 1034. The SGSN 1032 is at the same hierarchicallevel as the MSC 1008 in the GSM network. The SGSN controls theconnection between the GPRS network and the MS 1002. The SGSN also keepstrack of individual MS's locations and security functions and accesscontrols.

A Cell Broadcast Center (CBC) 14 communicates cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile phone customers who arelocated within a given part of its network coverage area at the time themessage is broadcast.

The GGSN 1034 provides a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1036. That is, the GGSNprovides interworking functionality with external networks, and sets upa logical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it is transferred to an external TCP-IP network1036, such as an X.25 network or the Internet. In order to access GPRSservices, the MS first attaches itself to the GPRS network by performingan attach procedure. The MS then activates a packet data protocol (PDP)context, thus activating a packet communication session between the MS,the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services can be used inparallel. The MS can operate in one of three classes: class A, class B,and class C. A class A MS can attach to the network for both GPRSservices and GSM services simultaneously. A class A MS also supportssimultaneous operation of GPRS services and GSM services. For example,class A mobiles can receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS can attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

A GPRS network 1030 can be designed to operate in three networkoperation modes (NOM1, NOM2 and NOM3). A network operation mode of aGPRS network is indicated by a parameter in system information messagestransmitted within a cell. The system information messages dictates a MSwhere to listen for paging messages and how to signal towards thenetwork. The network operation mode represents the capabilities of theGPRS network. In a NOM1 network, a MS can receive pages from a circuitswitched domain (voice call) when engaged in a data call. The MS cansuspend the data call or take both simultaneously, depending on theability of the MS. In a NOM2 network, a MS may not receive pages from acircuit switched domain when engaged in a data call, since the MS isreceiving data and is not listening to a paging channel. In a NOM3network, a MS can monitor pages for a circuit switched network whilereceived data and vice versa.

The IP multimedia network 1038 was introduced with 3GPP Release 5, andincludes an IP multimedia subsystem (IMS) 1040 to provide richmultimedia services to end users. A representative set of the networkentities within the IMS 1040 are a call/session control function (CSCF),a media gateway control function (MGCF) 1046, a media gateway (MGW)1048, and a master subscriber database, called a home subscriber server(HSS) 1050. The HSS 1050 may be common to the GSM network 1001, the GPRSnetwork 1030 as well as the IP multimedia network 1038.

The IP multimedia system 1040 is built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1043, a proxy CSCF (P-CSCF) 1042, and a serving CSCF (S-CSCF) 1044. TheP-CSCF 1042 is the MS's first point of contact with the IMS 1040. TheP-CSCF 1042 forwards session initiation protocol (SIP) messages receivedfrom the MS to an SIP server in a home network (and vice versa) of theMS. The P-CSCF 1042 may also modify an outgoing request according to aset of rules defined by the network operator (for example, addressanalysis and potential modification).

The I-CSCF 1043, forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. The I-CSCF 1043 may contact asubscriber location function (SLF) 1045 to determine which HSS 1050 touse for the particular subscriber, if multiple HSS's 1050 are present.The S-CSCF 1044 performs the session control services for the MS 1002.This includes routing originating sessions to external networks androuting terminating sessions to visited networks. The S-CSCF 1044 alsodecides whether an application server (AS) 1052 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromthe HSS 1050 (or other sources, such as an application server 1052). TheAS 1052 also communicates to a location server 1056 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of the MS 1002.

The HSS 1050 contains a subscriber profile and keeps track of which corenetwork node is currently handling the subscriber. It also supportssubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1050, a subscriber location function providesinformation on the HSS 1050 that contains the profile of a givensubscriber.

The MGCF 1046 provides interworking functionality between SIP sessioncontrol signaling from the IMS 1040 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown). It also controls the mediagateway (MGW) 1048 that provides user-plane interworking functionality(e.g., converting between AMR- and PCM-coded voice). The MGW 1048 alsocommunicates with other IP multimedia networks 1054.

Push to Talk over Cellular (PoC) capable mobile phones register with thewireless network when the phones are in a predefined area (e.g., jobsite, etc.). When the mobile phones leave the area, they register withthe network in their new location as being outside the predefined area.This registration, however, does not indicate the actual physicallocation of the mobile phones outside the pre-defined area.

FIG. 12 illustrates a PLMN block diagram view of an example architecturein which management of timer settings and/or retry criteria/mechanismsmay be incorporated. Mobile Station (MS) 1401 is the physical equipmentused by the PLMN subscriber. In one illustrative embodiment,communications device 200 may serve as Mobile Station 1401. MobileStation 1401 may be one of, but not limited to, a cellular telephone, acellular telephone in combination with another electronic device or anyother wireless mobile communication device.

Mobile Station 1401 may communicate wirelessly with Base Station System(BSS) 1410. BSS 1410 contains a Base Station Controller (BSC) 1411 and aBase Transceiver Station (BTS) 1412. BSS 1410 may include a single BSC1411/BTS 1412 pair (Base Station) or a system of BSC/BTS pairs which arepart of a larger network. BSS 1410 is responsible for communicating withMobile Station 1401 and may support one or more cells. BSS 1410 isresponsible for handling cellular traffic and signaling between MobileStation 1401 and Core Network 1440. Typically, BSS 1410 performsfunctions that include, but are not limited to, digital conversion ofspeech channels, allocation of channels to mobile devices, paging, andtransmission/reception of cellular signals.

Additionally, Mobile Station 1401 may communicate wirelessly with RadioNetwork System (RNS) 1420. RNS 1420 contains a Radio Network Controller(RNC) 1421 and one or more Node(s) B 1422. RNS 1420 may support one ormore cells. RNS 1420 may also include one or more RNC 1421/Node B 1422pairs or alternatively a single RNC 1421 may manage multiple Nodes B1422. RNS 1420 is responsible for communicating with Mobile Station 1401in its geographically defined area. RNC 1421 is responsible forcontrolling the Node(s) B 1422 that are connected to it and is a controlelement in a UMTS radio access network. RNC 1421 performs functions suchas, but not limited to, load control, packet scheduling, handovercontrol, security functions, as well as controlling Mobile Station1401's access to the Core Network (CN) 1440.

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 1430 is aradio access network that provides wireless data communications forMobile Station 1401 and User Equipment 1402. E-UTRAN 1430 provideshigher data rates than traditional UMTS. It is part of the Long TermEvolution (LTE) upgrade for mobile networks and later releases meet therequirements of the International Mobile Telecommunications (IMT)Advanced and are commonly known as a 4G networks. E-UTRAN 1430 mayinclude of series of logical network components such as E-UTRAN Node B(eNB) 1431 and E-UTRAN Node B (eNB) 1432. E-UTRAN 1430 may contain oneor more eNBs. User Equipment 1402 may be any user device capable ofconnecting to E-UTRAN 1430 including, but not limited to, a personalcomputer, laptop, mobile device, wireless router, or other devicecapable of wireless connectivity to E-UTRAN 1430. The improvedperformance of the E-UTRAN 1430 relative to a typical UMTS networkallows for increased bandwidth, spectral efficiency, and functionalityincluding, but not limited to, voice, high-speed applications, largedata transfer and IPTV, while still allowing for full mobility.

An example embodiment of a mobile data and communication service thatmay be implemented in the PLMN architecture described in FIG. 12 is theEnhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement forGPRS networks that implements an improved signal modulation scheme knownas 8-PSK (Phase Shift Keying). By increasing network utilization, EDGEmay achieve up to three times faster data rates as compared to a typicalGPRS network. EDGE may be implemented on any GSM network capable ofhosting a GPRS network, making it an ideal upgrade over GPRS since itmay provide increased functionality of existing network resources.Evolved EDGE networks are becoming standardized in later releases of theradio telecommunication standards, which provide for even greaterefficiency and peak data rates of up to 1 Mbit/s, while still allowingimplementation on existing GPRS-capable network infrastructure.

Typically Mobile Station 1401 may communicate with any or all of BSS1410, RNS 1420, or E-UTRAN 1430. In a illustrative system, each of BSS1410, RNS 1420, and E-UTRAN 1430 may provide Mobile Station 1401 withaccess to Core Network 1440. The Core Network 1440 may include of aseries of devices that route data and communications between end users.Core Network 1440 may provide network service functions to users in theCircuit Switched (CS) domain, the Packet Switched (PS) domain or both.The CS domain refers to connections in which dedicated network resourcesare allocated at the time of connection establishment and then releasedwhen the connection is terminated. The PS domain refers tocommunications and data transfers that make use of autonomous groupingsof bits called packets. Each packet may be routed, manipulated,processed or handled independently of all other packets in the PS domainand does not require dedicated network resources.

The Circuit Switched—Media Gateway Function (CS-MGW) 1441 is part ofCore Network 1440, and interacts with Visitor Location Register (VLR)and Mobile-Services Switching Center (MSC) Server 1460 and Gateway MSCServer 1461 in order to facilitate Core Network 1440 resource control inthe CS domain. Functions of CS-MGW 1441 include, but are not limited to,media conversion, bearer control, payload processing and other mobilenetwork processing such as handover or anchoring. CS-MGW 1440 mayreceive connections to Mobile Station 1401 through BSS 1410, RNS 1420 orboth.

Serving GPRS Support Node (SGSN) 1442 stores subscriber data regardingMobile Station 1401 in order to facilitate network functionality. SGSN1442 may store subscription information such as, but not limited to, theInternational Mobile Subscriber Identity (IMSI), temporary identities,or Packet Data Protocol (PDP) addresses. SGSN 1442 may also storelocation information such as, but not limited to, the Gateway GPRSSupport Node (GGSN) 1444 address for each GGSN where an active PDPexists. GGSN 1444 may implement a location register function to storesubscriber data it receives from SGSN 1442 such as subscription orlocation information.

Serving Gateway (S-GW) 1443 is an interface which provides connectivitybetween E-UTRAN 1430 and Core Network 1440. Functions of S-GW 1443include, but are not limited to, packet routing, packet forwarding,transport level packet processing, event reporting to Policy andCharging Rules Function (PCRF) 1450, and mobility anchoring forinter-network mobility. PCRF 1450 uses information gathered from S-GW1443, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources and other networkadministration functions. Packet Data Network Gateway (PDN-GW) 1445 mayprovide user-to-services connectivity functionality including, but notlimited to, network-wide mobility anchoring, bearer session anchoringand control, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS) 1463 is a database for user information,and stores subscription data regarding Mobile Station 1401 or UserEquipment 1402 for handling calls or data sessions. Networks may containone HSS 1463 or more if additional resources are required. Example datastored by HSS 1463 include, but is not limited to, user identification,numbering and addressing information, security information, or locationinformation. HSS 1463 may also provide call or session establishmentprocedures in both the PS and CS domains.

The VLR/MSC Server 1460 provides user location functionality. WhenMobile Station 1401 enters a new network location, it begins aregistration procedure. A MSC Server for that location transfers thelocation information to the VLR for the area. A VLR and MSC Server maybe located in the same computing environment, as is shown by VLR/MSCServer 1460, or alternatively may be located in separate computingenvironments. A VLR may contain, but is not limited to, user informationsuch as the IMSI, the Temporary Mobile Station Identity (TMSI), theLocal Mobile Station Identity (LMSI), the last known location of themobile station, or the SGSN where the mobile station was previouslyregistered. The MSC server may contain information such as, but notlimited to, procedures for Mobile Station 1401 registration orprocedures for handover of Mobile Station 1401 to a different section ofthe Core Network 1440. GMSC Server 1461 may serve as a connection toalternate GMSC Servers for other mobile stations in larger networks.

Equipment Identity Register (EIR) 1462 is a logical element which maystore the International Mobile Equipment Identities (IMEI) for MobileStation 1401. In a typical embodiment, user equipment may be classifiedas either “white listed” or “black listed” depending on its status inthe network. In one embodiment, if Mobile Station 1401 is stolen and putto use by an unauthorized user, it may be registered as “black listed”in EIR 1462, preventing its use on the network. Mobility ManagementEntity (MME) 1464 is a control node which may track Mobile Station 1401or User Equipment 1402 if the devices are idle. Additional functionalitymay include the ability of MME 1464 to contact an idle Mobile Station1401 or User Equipment 1402 if retransmission of a previous session isrequired.

While example embodiments of management of timer settings and/or retrycriteria/mechanisms have been described in connection with variouscomputing devices/processors, the underlying concepts may be applied toany computing device, processor, or system capable of implementingmanagement of timer settings and/or retry criteria/mechanisms. Thevarious techniques described herein can be implemented in connectionwith hardware or software or, where appropriate, with a combination ofboth. Thus, the methods and apparatuses of using and implementingmanagement of timer settings and/or retry criteria/mechanisms may beimplemented, or certain aspects or portions thereof, can take the formof program code (i.e., instructions) embodied in tangible storage mediahaving a tangible physical structure. Examples of tangible storage mediainclude floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a transientsignal per se. Further, a computer-readable storage medium is not apropagating signal per se. When the program code is loaded into andexecuted by a machine, such as a computer, the machine becomes anapparatus for implementing management of timer settings and/or retrycriteria/mechanisms. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile and non-volatile memory and/or storage elements), at least oneinput device, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and combined with hardwareimplementations.

The methods and apparatuses for using and implementing management oftimer settings and/or retry criteria/mechanisms also may be practicedvia communications embodied in the form of program code that istransmitted over some transmission medium, such as over electricalwiring or cabling, through fiber optics, or via any other form oftransmission, wherein, when the program code is received and loaded intoand executed by a machine, such as an EPROM, a gate array, aprogrammable logic device (PLD), a client computer, or the like, themachine becomes an apparatus for implementing management of timersettings and/or retry criteria/mechanisms. When implemented on ageneral-purpose processor, the program code combines with the processorto provide a unique apparatus that operates to invoke the functionalityof management of timer settings and/or retry criteria/mechanisms.

While management of timer settings and/or retry criteria/mechanisms hasbeen described in connection with the various embodiments of the variousfigures, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for implementing management of timer settings and/or retrycriteria/mechanisms without deviating therefrom. For example, oneskilled in the art will recognize that management of timer settingsand/or retry criteria/mechanisms as described in the present applicationmay apply to any environment, whether wired or wireless, and may beapplied to any number of such devices connected via a communicationsnetwork and interacting across the network. Therefore, management oftimer settings and/or retry criteria/mechanisms should not be limited toany single embodiment, but rather should be construed in breadth andscope in accordance with the appended claims.

What is claimed:
 1. An apparatus comprising: a processor; and memory coupled to the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising: attempting to establish communications with a first long term evolution network entity; when the attempt to establish communications with the first long term evolution network entity fails, waiting an amount of time equal to a value of a first timer associated with the first network entity before retrying an attempt to establish communications with the first long term evolution network entity; upon establishing communications with the first long term evolution network entity, subsequently attempting to establish communications with a second long term evolution network entity; and when the attempt to establish communications with the second long term evolution network fails, waiting an amount of time equal to a value of a second timer associated with the second long term evolution network entity before retrying an attempt to establish communications with the second long term evolution network entity.
 2. The apparatus of claim 1, wherein at least one of: the value of the first timer is based on an amount of data traffic on a long term evolution network; or the value of the second timer is based on an amount of data traffic on the long term evolution network.
 3. The apparatus of claim 1, wherein: a maximum number of times to retry establishing communications with the first long term evolution network entity is greater than a maximum number of times to retry establishing communications with the second long term evolution network entity.
 4. The apparatus of claim 1, wherein at least one of: a maximum number of times to retry establishing communications with the first long term evolution network entity is based on an amount of data traffic on a long term evolution network; or a maximum number of times to retry establishing communications with the second long term evolution network entity is based on an amount of data traffic on the long term evolution network.
 5. The apparatus of claim 1, the operations further comprising: receiving, from at least one of the first long term evolution network entity or the second long term evolution network entity, an indication of an amount of data traffic on a long term evolution network.
 6. The apparatus of claim 1, the operations further comprising: determining the value of the second timer.
 7. The apparatus of claim 1, the operations further comprising: determining a maximum number of times to retry establishing communications with the second long term evolution network entity.
 8. A method comprising: attempting to establish communications with a first long term evolution network entity; when the attempt to establish communications with the first long term evolution network entity fails, waiting an amount of time equal to a value of a first timer associated with the first network entity before retrying an attempt to establish communications with the first long term evolution network entity; upon establishing communications with the first long term evolution network entity, subsequently attempting to establish communications with a second long term evolution network entity; and when the attempt to establish communications with the second long term evolution network fails, waiting an amount of time equal to a value of a second timer associated with the second long term evolution network entity before retrying an attempt to establish communications with the second long term evolution network entity.
 9. The method of claim 8, wherein at least one of: the value of the first timer is based on an amount of data traffic on a long term evolution network; or the value of the second timer is based on an amount of data traffic on the long term evolution network.
 10. The method of claim 8, wherein: a maximum number of times to retry establishing communications with the first long term evolution network entity is greater than a maximum number of times to retry establishing communications with the second long term evolution network entity.
 11. The method of claim 8, wherein at least one of: a maximum number of times to retry establishing communications with the first long term evolution network entity is based on an amount of data traffic on a long term evolution network; or a maximum number of times to retry establishing communications with the second long term evolution network entity is based on an amount of data traffic on the long term evolution network.
 12. The method of claim 8, further comprising: receiving, from at least one of the first long term evolution network entity or the second long term evolution network entity, an indication of an amount of data traffic on a long term evolution network.
 13. The method of claim 8, further comprising: determining the value of the second timer.
 14. The method of claim 8, further comprising: determining a maximum number of times to retry establishing communications with the second long term evolution network entity.
 15. A computer-readable storage medium comprising executable instructions that when executed by a processor cause the processor to effectuate operations comprising: attempting to establish communications with a first long term evolution network entity; when the attempt to establish communications with the first long term evolution network entity fails, waiting an amount of time equal to a value of a first timer associated with the first network entity before retrying an attempt to establish communications with the first long term evolution network entity; upon establishing communications with the first long term evolution network entity, subsequently attempting to establish communications with a second long term evolution network entity; and when the attempt to establish communications with the second long term evolution network fails, waiting an amount of time equal to a value of a second timer associated with the second long term evolution network entity before retrying an attempt to establish communications with the second long term evolution network entity.
 16. The computer-readable storage medium of claim 15, wherein at least one of: the value of the first timer is based on an amount of data traffic on a long term evolution network; or the value of the second timer is based on an amount of data traffic on the long term evolution network.
 17. The computer-readable storage medium of claim 15, wherein: a maximum number of times to retry establishing communications with the first long term evolution network entity is greater than a maximum number of times to retry establishing communications with the second long term evolution network entity.
 18. The computer-readable storage medium of claim 15, wherein at least one of: a maximum number of times to retry establishing communications with the first long term evolution network entity is based on an amount of data traffic on a long term evolution network; or a maximum number of times to retry establishing communications with the second long term evolution network entity is based on an amount of data traffic on the long term evolution network.
 19. The computer-readable storage medium of claim 15, the operations further comprising: receiving, from at least one of the first long term evolution network entity or the second long term evolution network entity, an indication of an amount of data traffic on a long term evolution network.
 20. The computer-readable storage medium of claim 15, the operations further comprising: determining the value of the second timer. 